-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tie to the custom docker network for the devcontainers #1986
Conversation
🧪 Review environmenthttps://v3zrqml3zrsrikwhtgxzqycbo40xnjlr.lambda-url.ca-central-1.on.aws/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, app runs and communicates with the API container just fine using host.docker.internal
in the .env with Colima running.
chown -R vscode:vscode /workspaces/notification-admin | ||
sudo -u vscode -i -- /usr/local/bin/installations.sh | ||
# Install and setup dev environment | ||
installations.sh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was wondering how this script was called previously but could not find it. Does that look ok if I call it from here? cc @jzbahrai @whabanks @andrewleith
@@ -0,0 +1,33 @@ | |||
version: '3' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Having a docker-compose.yml file gives us more options to customize our VSCode devcontainers.
|
||
networks: | ||
notify-network: | ||
external: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will attach to the custom network defined in the API project, where it is created.
Summary | Résumé
Test instructions | Instructions pour tester la modification
Rebuild the devcontainer and make sure you can start the application again.
Also, having the latest API with related changes, you can now perform the following while the API devcontainer is also up and running: